Add per-computer launchers and preserve user window choices - #6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Configured computers can now be opened from normal desktop launcher entries. Add
launcher list/install/removeandopen: the desktop entry opens the configured default profile, waits for a matched window, reports failures through desktop notifications, and focuses an existing connection without duplication.Moonlight 6.1 hardcodes its app ID. Expose a stable desktop ID and exact class/title matching metadata, reject duplicate configured titles, and tag each owned final window by computer. Clear fullscreen once on a new stream window to handle Omarchy’s default rule, with durable tracking that preserves later user fullscreen and workspace choices across repeated opens and daemon restarts. No global window rules or placement changes are introduced.
Validation: 8 Rust tests, 30 Python tests, 14 daemon integration tests, format/Clippy, debug/release builds, and desktop-file validation. An installed MacBook entry was launched through GTK: windowed startup and tag verified, repeat launch reused one process, explicit fullscreen survived reopening and daemon restart, and disconnect restored the host display baseline. Two-host and temporary-window matching are covered by isolated integration tests. Input/audio usability still needs human confirmation.
The MacBook source-build launcher is installed locally; no package/release or generic Hypertile Scenes integration is included. All three CI jobs must pass before rebase merge into develop.